Skip to content

[minor] add support to install MAS Provisioner #1601

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 12 commits into
base: master
Choose a base branch
from
Open

Conversation

caroazad
Copy link
Contributor

Add support to install MAS Provisioner/Service Broker via gitops/saas-envs

@caroazad caroazad changed the title [patch] add support to install MAS Provisioner [minor] add support to install MAS Provisioner May 16, 2025
Copy link
Member

@whitfiea whitfiea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also add evidence of what testing has happened?

Comment on lines +286 to +310
sm_update_secret $SECRET_NAME_PROVISIONER "{\"git_token\": \"${GITHUB_PAT}\"}" "${TAGS}"
else
export SECRET_KEY_GITHUB_TOKEN=""
fi

if [ -n "$PAGERDUTY_KEY" ]; then
echo "- Update PAGERDUTY_KEY secret"
TAGS="[{\"Key\": \"source\", \"Value\": \"gitops_mas_provisioner\"}, {\"Key\": \"account\", \"Value\": \"${ACCOUNT_ID}\"}, {\"Key\": \"cluster\", \"Value\": \"${CLUSTER_ID}\"}]"
sm_update_secret $SECRET_NAME_PROVISIONER "{\"pd_key\": \"${PAGERDUTY_KEY}\"}" "${TAGS}"
else
export SECRET_KEY_PAGERDUTY=""
fi

if [ -n "$OCM_API_KEY" ]; then
echo "- Update OCM_API_KEY secret"
TAGS="[{\"Key\": \"source\", \"Value\": \"gitops_mas_provisioner\"}, {\"Key\": \"account\", \"Value\": \"${ACCOUNT_ID}\"}, {\"Key\": \"cluster\", \"Value\": \"${CLUSTER_ID}\"}]"
sm_update_secret $SECRET_NAME_PROVISIONER "{\"ocm_api\": \"${OCM_API_KEY}\"}" "${TAGS}"
else
export SECRET_KEY_OCM_API=""
fi

if [ -n "$CSB_CA_CERT" ]; then
echo "- Update CSB_CA_CERT secret"
TAGS="[{\"Key\": \"source\", \"Value\": \"gitops_mas_provisioner\"}, {\"Key\": \"account\", \"Value\": \"${ACCOUNT_ID}\"}, {\"Key\": \"cluster\", \"Value\": \"${CLUSTER_ID}\"}]"
sm_update_secret $SECRET_NAME_PROVISIONER "{\"cert\": \"${CSB_CA_CERT}\"}" "${TAGS}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All these calls are updating the same secret, this will cause all the keys to be removed that were previously present i.e. if the CSB_CA_CERT is set then the secret will only have one key called cert and all the previous keys that might be set i.e. ocm_api etc will be lost

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants